Hello,

i am capturing a new Windows 8-image.

I have created a seperate task-sequence for Windows 8-capture with the DVD of windows 8 as setup-files.

After rebooting to Winpe my deployment this is hanging op "create wim"

What to do?

It is advisable you capture wim from script runnning on the machine (which image needs to be captured)

You can use imagex tool to capture image manually...

Hello Srk,

the image starts capturing after 20 minutes.

For windows 7 this will start after a few seconds...

Why is this during for 20 minutes for windows 8?

what does the log say?

Hi Shrek,

see the screenshots (many many lines of these in the BDD.LOG)

Anybody who has fix for this windows 8 log-issue?

I've been seeing the same thing in our environment. It hung for 24 minutes before actually committing to creating the WIM. I theorized that upgrading to the ADK for 8.1 and MDT 2013 would resolve this, surely, but no. Interested in finding a resolution for this!

• Marked as answer by Keith GarnerMVP, Moderator Wednesday, October 23, 2013 6:11 PM

Yup, it's slow to start up. Not sure why. Shouldn't be a blocking issue, just slow.

In windows 7 this was something with ADK/WAIK.

So maybe a issue with ADK?

i'm having exactly the same issue on a Capture TS for Windows 8 using MDT 2013. It always takes about 20 minutes for the create wim step to start. Any update on how to solve this? Thank you!

• Edited by Stefan Schipper Sunday, February 09, 2014 9:25 PM

I did some research into this today and it seems the image is actually being captured during this process.  If you watch the %deployroot%\capture directory, you can see the image is being captured.  It's a strange bug.. definitely not stuck, just not reporting the time remaining.

I checked this today, I can see the file is created in the captures directory during this step. However no data is actually transferred until the next step kicks in. I can tell because the file size is 0KB right the way up to the next step.

Therefore, for me at least, it seems the process is hanging here. It is annoying as this causes the capture to take much longer than it used to. Anyone have any ideas how to fix this, or an explanation for the delay?

I can confirm this only happens on Windows 8 captures, 7 begins within a few moments.

 

• Edited by Niallenev Wednesday, May 07, 2014 11:20 AM

Installing this updated Windows Assessment and Deployment Kit seemed to fix the hanging on the 'Create WIM' action for Windows 8 captures:

http://www.microsoft.com/en-us/download/details.aspx?id=39982

• Proposed as answer by Niallenev Wednesday, May 07, 2014 12:10 PM

Hi, I am also getting stuck in the wim creation. I am using a virtual machine (VirtualBox) so I am able to take snapshots and so I have tried many times the same procedure. After the SysPrep, my virtual machine boots into the LiteTouch Installation and everything seems fine, the Capturing Process is slowly moving and I can see in my Captures-folder on my MDT-server that the wim-image is steadily growing. But, after some time it stops, and it can be after 1% or 6% or 9%, it is random, and I can see every time the size of the wim-file is different as well. Sometimes bigger, sometimes smaller, but I haven't been able to go beyond 9% of the capturing process, neither over 1 GB of the captured wim file. And please note that the machine completely freezes/hangs, mouse cursor not moving, it just sits there for unlimited time, no change in the size of the wim-file either on the MDT-server (in the Captures folder). Anyone has any ideas? 

I am using Windows Server 2012 R2 (x64), MDT2013, ADK and the OS I am trying to capture is Win7Prox86.

The Task Sequence is standard SysPrep and Capture, although I have disabled the Inject drivers for WinXP and WinServer2003.

Would be great to know the answer to this problem, so if anyone knows or have any suggestions, please let us know!

• Edited by Hans Kamizi 3 hours 22 minutes ago